Crash Finder Overview

Crash Finder allows the user to isolate translations that cause crashes of the localized application, and catch the localization bugs at the early stage of the localization process. Application crash may be caused by memory overlays due to string expansion, changes in non-translatable code, and errors in translation of format specifiers. Isolating error-containing elements is a tedious, trial-and-error practice with most software localization suites.  Lingobit Localizer allows the user to automate this process.

Crash Finder can help the user solve most common Quality Assurance issues. If the application functions incorrectly after the Pseudo Translation, Crash Finder allows the user to isolate all crash-inducing elements. Similarly, Crash Finder can be started during the actual localization process, after some of the localizable data is translated.

Crash Finder executes a series of launches of the localized application to detect the exact position of error-containing elements. Crash Finder applies as little as 10 launches to test an application containing 1000 translated elements. All errors found during the application file execution are isolated in one session.